Contextual Security Analysis

As DryRun Security performs checks, we’ll summarize them here. You can always dive into the detailed results in the section below for checks.

Chat with your AI-powered Security Buddy by typing @dryrunsecurity followed by your question into a comment.
Example: @dryrunsecurity What are common security issues with web application cookies?

Install and configure more repositories at DryRun Security

Hi @grendel513,

I would like to understand why you resolved my review. Could you please comment on that?

Best Regards

Hi @grendel513,

I would like to understand why you resolved my review. Could you please comment on that?

Best Regards

My comment specifically stated why: Keeping this a separate parser is the correct implementation to allow for its own deduplication which is what we are trying to solve for. Additionally having to individual parsers is easier to troubleshoot should issues arise, and has a the benefit of not affecting other tool ingestion if there is something wrong.

Moving forward we will be asking that new parsers be single threaded in function, as having parsers that parse multiple file types creates issues with debugging, deduplication, and the ability to have a separate deduplication configuration.

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

@dryrunsecurity What are common security issues with web application cookies?

Powered by DryRun Security

Hi @grendel513,
I would like to understand why you resolved my review. Could you please comment on that?
Best Regards

My comment specifically stated why: Keeping this a separate parser is the correct implementation to allow for its own deduplication which is what we are trying to solve for. Additionally having to individual parsers is easier to troubleshoot should issues arise, and has a the benefit of not affecting other tool ingestion if there is something wrong.

Moving forward we will be asking that new parsers be single threaded in function, as having parsers that parse multiple file types creates issues with debugging, deduplication, and the ability to have a separate deduplication configuration.

Thank you for clarification. 😄 I understand your logic.
What if we advance the parser structure in a way that file stuctures are automatically recognized (e.g. look at RustyHog) and then deduplication could be implemented for the subfile types (e.g. Deduplication for GottingenHog (RustyHog) etc.)
This whole topic is pretty complicated as there are pros and cons in both directions, but for beginners it would be easier if the number of parsers to be selected within a vendor is limited and the logic within DefectDojo handles the rest.
One way could also be which was implemented in veracode:

1. entry is a single parser for a vendor
2. parser recognizes the file type (subscanner)
3. individual deduplication and scannertype recognition (e.g. like in veracode + rustyhog)

If you (the maintainers) will provide guidelines for the future setup regarding parsers and how to solve the problem the best way, I would like to help here to improve this.